feat: Transfer frontend-template-application improvements#944
Conversation
|
Thanks for the pull request, @filippovskii09! This repository is currently maintained by Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review. 🔘 Get product approvalIf you haven't already, check this list to see if your contribution needs to go through the product review process.
🔘 Provide contextTo help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:
🔘 Get a green buildIf one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green. DetailsWhere can I find more information?If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources: When can I expect my changes to be merged?Our goal is to get community contributions seen and reviewed as efficiently as possible. However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:
💡 As a result it may take up to several weeks or months to complete a review and merge your PR. |
package.json
Outdated
| "lint": "fedx-scripts eslint --ext .js --ext .jsx .", | ||
| "lint:fix": "fedx-scripts eslint --fix --ext .js --ext .jsx .", | ||
| "stylelint": "stylelint \"plugins/**/*.scss\" \"src/**/*.scss\" \"scss/**/*.scss\" --config .stylelintrc.json", | ||
| "lint": "npm run stylelint && fedx-scripts eslint --ext .js --ext .jsx --ext .ts --ext .tsx .", |
There was a problem hiding this comment.
[nit]: Please add type checking to the linter
| "@edx/frontend-component-footer": "^14.9.2", | ||
| "@edx/frontend-component-header": "^8.0.0", |
There was a problem hiding this comment.
"@edx/frontend-component-header": "^8.0.0",
"@edx/frontend-component-footer": "^14.9.2",
package.json
Outdated
| "@edx/frontend-component-header": "^8.0.0", | ||
| "@edx/frontend-platform": "^8.3.0", | ||
| "@edx/openedx-atlas": "^0.7.0", | ||
| "@edx/paragon": "^21.5.6", |
There was a problem hiding this comment.
[important]: Please remove this old paragon package
package.json
Outdated
| "@types/node": "^24.7.2", | ||
| "ajv": "^6.12.6", | ||
| "ajv-keywords": "^3.5.2", |
There was a problem hiding this comment.
[important]: Please check if we really need these packages.
There was a problem hiding this comment.
i removed this packages and test local, they were unnecessary
There was a problem hiding this comment.
Thanks! Resolved
package.json
Outdated
| "jest": "30.2.0", | ||
| "stylelint": "^15.10.0", | ||
| "stylelint-config-standard": "^39.0.1", | ||
| "stylelint-scss": "^4.4.0" |
There was a problem hiding this comment.
[important]: Please check if we really need these packages.
There was a problem hiding this comment.
i removed this packages and test local, they were unnecessary too
d635f85 to
3a3d7e9
Compare
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #944 +/- ##
======================================
Coverage 0.00% 0.00%
======================================
Files 2 3 +1
Lines 7 24 +17
======================================
- Misses 7 24 +17 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
I took this configuration for .stylelintrc.json from this PR openedx/frontend-app-catalog#2
There was a problem hiding this comment.
Is this the correct link openedx/openedx-platform#37480?
There was a problem hiding this comment.
you're right, incorrect link, changed
There was a problem hiding this comment.
[inform]: @bydawen is currently working on creating a separate issue to address the linter-related questions that came up during this discussion: openedx/frontend-app-catalog#2 (comment). So in the future, we might have fewer overrides and more unified configurations.
package.json
Outdated
| "@openedx/paragon": "^23.14.8", | ||
| "core-js": "3.46.0", | ||
| "prop-types": "15.8.1", | ||
| "react": "17.0.2", |
There was a problem hiding this comment.
I noticed that in the PR we’re transferring changes from, there was an upgrade of React and some other libraries.
Let’s bring those updates over as well and make sure everything works correctly.
There was a problem hiding this comment.
The libraries that were removed or updated in that PR should also be removed or updated in this one.
There was a problem hiding this comment.
Removed and update packages
|
@filippovskii09 should the eslint configuration from the original PR we’re transferring changes from? You’ve transferred the stylelint config, but the eslint configuration hasn’t been brought over. |
@PKulkoRaccoonGang you're right, added that |
|
@brian-smith-tcril we recently worked together on openedx/frontend-app-catalog#2, which set up frontend-template-application for the new Catalog MFE. As part of that PR, we transferred all potentially necessary changes for the template repository - including linter configurations, React version upgrade, and TypeScript support. Please take a look when you have a chance. Thank you! |
arbrandes
left a comment
There was a problem hiding this comment.
Looks great! Thanks for this!
|
Do you mind resolving conflicts so we can merge it in? |
|
@arbrandes conflicts were resolved |
|
Apologies for the delay in merging! |
Description
Transfer frontend-template-application improvements
Supporting information
As part of the work on creating a new MFE Catalog, frontend-template-application was taken as a template. Improvements and optimizations were made (in this PR) that would be useful to transfer to the upstream frontend-template-application (master branch) repository so that the development of further new MFEs would start with a template that is more prepared for this.
Testing instructions
Please provide detailed step-by-step instructions for testing this change.
Deadline
"None" if there's no rush, or provide a specific date or event (and reason) if there is one.
Other information
Include anything else that will help reviewers and consumers understand the change.
Note
The changes implemented in this PR were tested in the new MFE.